Conversation
yingjianwu98
force-pushed
the
yingjianw/roaringBitMap
branch
2 times, most recently
from
9760f90 to
42ccaef
Compare
supporting roaringBitMap supporting roaringBitMap rename
yingjianwu98
force-pushed
the
yingjianw/roaringBitMap
branch
from
42ccaef to
94a7c6a
Compare
kevinjqliu
left a comment
kevinjqliu
left a comment
There was a problem hiding this comment.
I just saw this PR. Thank you @yingjianwu98
Do you know rebasing off main? Let's try to get this in 😄
|
This pull request has been marked as stale due to 30 days of inactivity. It will be closed in 1 week if no further activity occurs. If you think that's incorrect or this pull request requires a review, please simply write any comment. If closed, you can revive the PR at any time and @mention a reviewer or discuss it on the dev@iceberg.apache.org list. Thank you for your contributions. |
|
This pull request has been closed due to lack of activity. This is not a judgement on the merit of the PR in any way. It is just a way of keeping the PR queue manageable. If you think that is incorrect, or the pull request requires review, you can revive the PR at any time. |
2 participants
Rationale for this change
This is the first change to support deletion vector write in pyiceberg, where we build an abstraction on top of the Bitmap for various operations.
Jave implementation for reference
Are these changes tested?
Yes, I have added all tests from Java except one that validates the ByteOrder as python bytes does not support Order like Java ByteBuffer
Are there any user-facing changes?
No, this is a new class that is currently not used in any existing code path.